Method and apparatus for interfacing synchronous core network with asynchronous radio network

ABSTRACT

A method and apparatus for interfacing a synchronous core network with an asynchronous radio network in a next-generation mobile telecommunications system is disclosed. The method includes: a) selecting a function necessary to map a synchronous message to an asynchronous message; b) determining whether the synchronous message is to be transmitted to the mobile station or not; c) storing information necessary to map the synchronous message to the asynchronous message if the synchronous message is to transmitted to the mobile station, d) mapping parameters in the synchronous message to those in the asynchronous message, thereby generating the asynchronous message; e) discarding the message not to be transmitted to the mobile station after storing parameters included in the message not to be transmitted onto a predetermined device; and f) transmitting the asynchronous message to the radio resource controller.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.12/212,118, filed Sep. 17, 2008, which is a continuation of U.S. patentapplication Ser. No. 11/022,497, filed Dec. 22, 2004 (now U.S. Pat. No.7,443,881), which is a divisional of U.S. patent application Ser. No.09/628,316, filed Jul. 28, 2000 (now U.S. Pat. No. 6,853,852), whichclaims priority to Korean Patent Application No. 1999-30927, filed Jul.28, 1999, to Korean Patent Application No. 1999-30928, filed Jul. 28,1999, to Korean Patent Application No. 1999-35876, filed Aug. 27, 1999,and to Korean Patent Application No. 1999-40165, filed Sep. 17, 1999.All of these applications are incorporated herein by reference in theirentirety.

FIELD

The present disclosure relates to a method and apparatus for interfacinga synchronous core network with an asynchronous radio network; and, moreparticularly to a method and apparatus for interfacing a synchronouscore network with an asynchronous radio network in a next-generationmobile telecommunications system.

BACKGROUND

In a conventional synchronous mobile telecommunication system, asynchronous mobile station is connected to a synchronous radio network(for example, a CDMA-2000 radio network), and an ANSI-41 network isconnected to a core network.

In a conventional asynchronous mobile telecommunication system, anasynchronous mobile station is connected to an asynchronous radionetwork (for example, a UMTS (universal mobile telecommunicationssystem) Terrestrial Radio Access Network (UTRAN)), and a global systemfor mobile communications-mobile application part (GSM-MAP) network isconnected to a core network.

FIG. 1 shows core network interface architectures of the conventionalsynchronous/asynchronous mobile telecommunication systems as mentionedabove.

FIG. 1A is a view showing the core network interface architecture of theconventional synchronous mobile telecommunications system. In thisdrawing, the reference numeral 110 denotes a synchronous mobile station,120 denotes a synchronous radio network (e.g., a code division multipleaccess-2000 (CDMA-2000) radio network) which performs a data interfacingoperation with the synchronous mobile station 110 and includes asynchronous base transceiver station/base station controller (BTS/BSC),and 130 denotes a synchronous core network which is connected to thesynchronous radio network 120 and includes a synchronous mobile servicesswitching center (MSC) 131 and an ANSI-41 network 133.

In the above core network interface architecture of the conventionalsynchronous mobile telecommunication system, the synchronous mobilestation 110 can be connected to only the synchronous radio network 120as well known to one skilled in the art, which is in turn connected tothe synchronous core network 130, thereby allowing the synchronousmobile station 110 to be interfaced with only the synchronous corenetwork 130.

FIG. 1B is a view showing the core network interface architecture of theconventional asynchronous mobile telecommunication system. In thisdrawing, the reference numeral 140 denotes an asynchronous mobilestation, 150 denotes an asynchronous radio network (i.e., a UTRAN) whichincludes a base transceiver station (BTS) and a radio network controller(RNC), and 160 denotes an asynchronous core network which includes anasynchronous mobile services switching center (MSC) 161 connected to theasynchronous radio network 150 and a GMS-MAP network 163 connection tothe asynchronous MSC 161.

In the above core network interface architecture of the conventionalasynchronous mobile telecommunications system, the asynchronous mobilestation 140 is connected to the asynchronous radio network 150 (e.g.,UTRAN) which is in turn connected to the asynchronous core network 160,thereby allowing the asynchronous mobile station 140 to perform a datainterfacing operation with the asynchronous core network 160.

FIG. 2 shows layer protocol structures of the conventional mobiletelecommunication systems as mentioned above.

FIG. 2A is a view showing the layered protocol structure of theconventional synchronous mobile telecommunications system. In thisdrawing, the reference numeral 110 denotes a synchronous mobile station,120 a synchronous radio network and 50 a synchronous core networkconnected to the synchronous radio network 130.

The synchronous mobile station 110 comprises a layer3 111, a layer2 114and a layer1 115. The layer3 111 includes a synchronous call control(CC) entity 113 for a call management and a synchronous mobilitymanagement (MM) entity 112 for a mobility management.

The layer1 115 is a physical layer which offers data transport servicesto higher layers and transfers transport blocks over a radio interface.

The layer2 114 is a data link layer which includes the following sublayers, a medium access control (MAC) sub layer and a radio link control(RLC) sub layer. However, the sub layers are not shown in this drawing.

The MAC sub layer offers data transfer services on logical channels to ahigher layer, the RLC sub layer, and on transport channels to a lowerlayer, the physical layer 36. The MAC sub layer is responsible formapping of the logical channel onto the appropriate transports channel.

The RLC sub layer offers data transfer services on primitive to a higherlayer and on logical channels to a lower layer, MAC sub layer. Also, theRLC sub layer performs an error correction, a duplicate detection, aciphering and a flow control of the data.

The layer3 114 is a network layer which includes the following sublayers, a synchronous radio resource (RR) sub layer, a synchronous callcontrol (CC) entity 113 and a mobility management (MM) entity 112. Inthe synchronous system, the synchronous RR sub layer is not apparentlyseparated from the others in the layer3 111.

The RR sub layer offers data transfer services on primitive to a lowerlayer, RLC sub layer, and handles a control plane signaling of thelayer3 111 between a mobile station and a synchronous radio network. TheRR sub layer manages a radio resource. Also, the RR sub layerassigns/re-configures/releases the radio resource to the mobilestation/radio network.

The CC entity 113 handles a call control signaling of layer3 between themobile stations and the synchronous radio network.

The MM entity 112 handles a mobility management signaling of layer 3between the mobile stations and the synchronous radio network.

The layers 3 to 1111, 114 and 115 in the synchronous mobile station 110communicate with corresponding layers 121, 122 and 123 in thesynchronous radio network 120.

The synchronous radio network 120 comprises a layer3 121, a layer2 122and a layer 1 123. The layers 3 to 1121, 122 and 123 in the synchronousradio network 120 correspond respectively to those in the synchronousmobile station 110.

The layers 3 to 1, 121, 122 and 123 in the synchronous radio network 120communicate with corresponding layers in the synchronous mobile station110 and the synchronous core network 130.

The synchronous core network 130 comprises a layer3 131, a layer2 134and a layer 1 135. The layers 3 to 1 in the synchronous radio network130 correspond respectively to those in the synchronous radio network120.

The layers 3 to 1131, 134 and 135 in the synchronous core network 130communicate with corresponding layers 121, 122 and 123 in thesynchronous radio network 120.

In the conventional synchronous mobile station and radio network as thelayered protocol structure, the synchronous mobile station 110 receivesa Sync channel message from the synchronous radio network 120 over aSynch channel and acquires information necessary to its connection tothe synchronous core network 130, including information related to thesynchronous core network 130 and information about the synchronous radionetwork 120, from the received Sync channel message.

In other words, for interfacing with the synchronous ANSI-41 network viathe synchronous radio network, the synchronous mobile station acquiressystem information (i.e., information related to the radio network andcore network) after it is powered on.

Information elements are written in the Sync channel message received bythe synchronous mobile station, as follows:

a) Protocol Revision Level: 8 bits,

b) Minimum Protocol Revision Level: 8 bits,

c) System Identification: 15 bits,

d) Network Identification: 16 bits,

e) Pilot Pseudo Noise (PN) sequence offset index: 9 bits,

f) Long Code State: 42 bits,

g) System Time: 36 bits,

h) The number of Leap seconds that have occurred since the start ofSystem Time: 8 bits,

i) Offset of local time from System Time: 6 bits,

j) Daylight savings time indicator: 1 bit,

k) Paging Channel data Rate: 2 bits,

l) Frequency assignment: 11 bits,

m) Extended frequency assignment: 11 bits, and

n) Orthogonal transmit diversity mode: 2 bits.

The synchronous mobile station stores the following information elementsfrom the received Sync channel message in its memory:

a) Protocol Revision Level: 8 bits,

b) Minimum Protocol Revision Level: 8 bits,

c) System Identification: 15 bits,

d) Network Identification: 16 bits,

e) Pilot PN sequence offset index: 9 bits,

f) Long Code State: 42 bits,

g) System Time: 36 bits,

h) Paging Channel Data Rate: 2 bits, and

i) Orthogonal transmit diversity mode: 2 bits.

FIG. 2B is a view showing the layered protocol structure of theconventional asynchronous mobile telecommunications system. In thisdrawing, the reference numeral 140 denotes an asynchronous mobilestation, 150 an asynchronous radio network (e.g., UTRAN) and 160 anasynchronous core network.

The asynchronous mobile station 140 comprises a non-access stratum (NAS)part, a layer3 144, a layer2 145, and a layer1 146. In particular, thelayer3 144 includes an access stratum (AS) part. The NAS part includesan asynchronous call control (CC) entity 143 for management of a calland an asynchronous mobility management (MM) entity 142 for managementof a mobility. The AS part includes an asynchronous radio resourcecontrol (RRC) block. In the asynchronous system, the asynchronous RRCsub layer is apparently separated from the NAS part. Functions of theasynchronous RRC sub layer are the same as those of the synchronous RRsub layer.

The asynchronous radio network 150 comprises a layer3 151, a layer2 152,and a layer1 153. The layer3 151 of the asynchronous radio network 150has no NAS part having an asynchronous CC entity and an asynchronous MMentity. The layers 3 to 1 of the asynchronous radio network 150 areconnected and correspond respectively to those in the asynchronousmobile station 140 and those in the asynchronous core network 160.However, since the asynchronous radio network 150 does not have the NASpart, i.e., the asynchronous CC entity and the asynchronous MM entity,the NAS parts of the asynchronous mobile station 140 and asynchronouscore network 160 are coupled to each other not through the asynchronousradio network 150.

The asynchronous core network 160 comprises a NAS part 161 connected tothat of the asynchronous mobile station 140, a layer3 164 having a ASpart (not shown in FIG. 2B), a layer2 165 and a layer 1 166 connectedrespectively to those in the asynchronous radio network 150. The NASpart comprises an asynchronous CC entity 163 for management of a calland an asynchronous MM entity 162 for management of mobility.

Functions of the layer 3 to 1 of the asynchronous system are similarwith those of the synchronous system except for an operating type.Therefore, for convenience, detailed description of the layer 3 to 1will be skipped.

The more detailed descriptions about layered protocol structures arewell taught in 3^(rd) Generation partnership Project (3GPP), TechnicalSpecification group (TSG)-Radio Access Network (RAN): 3G TS25.301 (RadioInterface Protocol Architecture), 3G TS25.302 (Services provided by thephysical layer), 3G TS25.321 (MAS Protocol Specification), 3G TS25.322(RLC Protocol Specification) and 3G TS25.331 (RRC ProtocolSpecification) in detail.

In the conventional asynchronous mobile station and radio network havingthe layered protocol structure, the asynchronous mobile station 140receives a system information message from the asynchronous radionetwork 150 over a broadcast control channel (BCCH) and acquiresinformation necessary to its connection to the asynchronous core network160, including information related to the asynchronous core network 160and information about the asynchronous radio network 150, from thereceived system information message.

IMT-2000 systems are the third generation systems which aim to unify thevarious mobile communication networks and services into one to providemany mobile communication services. The systems can provide multimediaservices under multi-environments through various air-interfaces andhigh capacity. Also, in the aspect of services, the systems can providemultimedia services of speech, image and data up to the rate of 2 Mbpsand international roaming. And, in the aspect of network, the systemsare total systems which are based on ATM networks and combine fixed andwireless systems.

IMT-2000 system requires new system concept, a high-level adaptationtechnology, and a novel network technology, as well all conventionaltechnologies which were already adopted in the second digital cellularsystem.

As described above, in the next-generation mobile telecommunicationsystem such as the IMT-2000 system, either the GSM-MAP network used inthe above conventional asynchronous mobile telecommunications system orthe ANSI-41 network used in the above conventional synchronous mobiletelecommunications system should be employed as a core network in orderto perform an international roaming in a synchronous or asynchronousmobile telecommunications system of an IMT-2000 system.

According to network deployment scenarios, the IMT-2000 system can havethe following four interface architectures; first: synchronous mobilestation—synchronous radio network—synchronous ANS1-41 network, second:synchronous mobile station—synchronous radio network—asynchronousGSM-MAP network, third: asynchronous mobile station—asynchronous radionetwork—synchronous ANSI-41 network, and fourth: asynchronous mobilestation—asynchronous radio network—asynchronous GSM-MAP network.

FIG. 3 is a view showing a protocol stack structure for interfacing amobile station and a base station with a core network in anext-generation mobile telecommunications system.

Referring to FIG. 3, it is illustrated a protocol stack structure forinterfacing a mobile station and a base station with a core networkhaving the same or a different operating type with/from the mobilestation and the base station in a next-generation mobiletelecommunications system such as the IMT-2000 system.

The asynchronous mobile station includes a physical layer, a mediumaccess layer, a radio link layer, a radio resource layer, a mobilitymanagement entity and a call control entity. Also, the asynchronousmobile station includes extensions and hooks.

The extension performs a mapping function between the asynchronousmobile station and the synchronous core network. The hook providesenvironments for performing a mapping function between the asynchronousmobile station and the synchronous core network.

The asynchronous base station includes the same elements with those ofthe asynchronous mobile station.

Concepts of the protocol stack structure for interfacing a mobilestation and a base station and a core network are already defined,however, specific functions the protocol stack structure are not yetdefined and proposed.

The conventional synchronous mobile station and radio network have adisadvantage in that the synchronous mobile station cannot be interfacedwith any other networks than a synchronous core network connectedthereto because synchronous mobile station cannot recognize anasynchronous message from an asynchronous core network, the conventionalsynchronous mobile station cannot communicate with the asynchronous corenetwork.

Similarly, the conventional asynchronous mobile station and radionetwork have a disadvantage in that the asynchronous mobile stationcannot be interfaced with any other networks than an asynchronous corenetwork because asynchronous mobile station cannot recognize asynchronous message from a synchronous core network, the conventionalasynchronous mobile station cannot communicate with the synchronous corenetwork.

SUMMARY OF THE INVENTION

Therefore, it is an object of the invention to provide a method andapparatus for interfacing a synchronous core network with anasynchronous mobile station in a next-generation mobiletelecommunication system.

It is another object of the invention to provide a method and apparatusfor transmitting a CC/MM entity between a synchronous core networkbetween an asynchronous mobile station in a next-generation mobiletelecommunication system.

It is further another object of the invention to provide a method andapparatus for mapping a message transmitted between a synchronous corenetwork and an asynchronous mobile station in a next-generation mobiletelecommunication system.

It is still further another object of the invention to provide a methodand apparatus for transmitting a message between a synchronous corenetwork to an asynchronous mobile station in a next-generation mobiletelecommunication system.

In accordance with an aspect of the preset invention, there is provideda method for mapping a message in order to interface a synchronous corenetwork with an asynchronous radio network a base station (BS), the basestation having a radio resource controller, a radio link controller, amedium access controller and a physical controller, the methodcomprising the steps of: a) selecting a function necessary to map asynchronous message to an asynchronous message; b) determining whetherthe synchronous message is to be transmitted to the mobile station ornot; c) storing information necessary to map the synchronous message tothe asynchronous message if the synchronous message it to be transmittedto the mobile station; d) mapping parameters in the synchronous messageto those in the asynchronous message, thereby generating theasynchronous message; e) discarding the message not to be transmitted tothe mobile station after storing parameters included in the message notto be transmitted onto a predetermined device; and f) transmitting theasynchronous message to the radio resource controller.

In accordance with another aspect of the present invention, there isprovided a method for transmitting a message from a synchronous corenetwork to an asynchronous radio network having a base station (BS), thebase station having a radio resource controller, a radio linkcontroller, a medium access controller and a physical controller, themethod comprising the steps of: receiving a synchronous message from thesynchronous core network; and mapping the synchronous message to anasynchronous message based on information from supporting entitiesplaced in the radio resource controller, the radio link controller, themedium access controller and the physical controller.

In accordance with further another aspect of the present invention,there is provided a method for transmitting a message from anasynchronous radio network to a synchronous core network, the radionetwork having a base station (BS), a mobile station and the basestation respectively having a radio resource controller, a radio linkcontroller, a medium access controller and a physical controller, themethod comprising the steps of: receiving an asynchronous message; andmapping the asynchronous message to a synchronous message based oninformation from supporting entities placed in the radio resourcecontroller, the radio link controller, the medium access controller andthe physical controller.

In accordance with still further another aspect of the presentinvention, there is provided a method for transmitting a callcontrol/mobility management (CC/MM) message from a synchronous corenetwork to an asynchronous radio network, the radio network having amobile station (MS), a base transceiver station (BTS) and a base stationcontroller (BSC), the method comprising the steps of: a) receiving amessage received from the synchronous core network, the message havingparameters to be bypassed and parameters not to be bypassed; b)determining whether the parameters are to be bypassed or not; c)bypassing the parameters to be bypassed to the mobile station if theparameters are to be bypassed; and d) processing the parameters not bebypassed and generating a processed message if not.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects and features of the instant invention willbecome apparent from the following description of preferred embodimentstaken in conjunction with the accompanying drawings, in which:

FIG. 1A is a view showing the core network interface architecture of theconventional synchronous mobile telecommunications system;

FIG. 1B is a view showing the core network interface architecture of theconventional asynchronous mobile telecommunications system;

FIG. 2A is a diagram of layer protocols of a conventional synchronousmobile telecommunications system;

FIG. 2B is a diagram of layer protocols of a conventional asynchronousmobile telecommunications system;

FIG. 3 is a view showing a protocol stack structure for interfacing amobile station and a base station with a core network in anext-generation mobile telecommunications system;

FIG. 4 is a diagram of protocol layers of an asynchronous mobile stationand an asynchronous radio network for interfacing with a synchronouscore network in accordance with an embodiment of the present invention;

FIG. 5A to 5D are block diagrams of supporting entities in accordancewith the preset invention;

FIG. 6 is a block diagram of a mapping entity in accordance with thepreset invention;

FIG. 7 is a flow chart illustrating a method for transmitting a messagebetween an asynchronous radio network and a synchronous core network;

FIG. 8 is a block diagram of a device for mapping a call control/mobilemanagement (CC/MM) message between an asynchronous radio network and asynchronous core network in accordance with another embodiment of thepresent invention;

FIG. 9 is a flow chart illustrating a method for determining whether theCC/MM message is bypassed or not;

FIG. 10 is a flow chart illustrating a method for mapping a synchronousCC/MM message to an asynchronous CC/MM message;

FIG. 11 is a flow chart illustrating a method for processing informationused for the radio network; and

FIG. 12 is a diagram showing operations for converting a synchronousauthentication request message to an asynchronous message.

DETAILED DESCRIPTION

Hereinafter, preferred embodiments of the present invention will bedescribed in detail with reference to the accompanying drawings.

FIG. 4 is a diagram of protocol layers of an asynchronous mobile stationand an asynchronous radio network for interfacing the asynchronous radionetwork with a synchronous core network in accordance with the presentinvention.

The reference numeral 400 denotes an asynchronous radio network. Thebase station 400 includes a synchronous protocol processing block 402, amapping entity 404, a call control/mobility management (CC/MM) entity406, a radio resource controller 408, a radio link controller 410, amedium access controller 412, a physical layer 414 and a transport block416.

The radio resource controller 408, the radio link controller 420, themedium access controller 412 and the physical layer 414 respectivelyinclude a supporting entity 408 a, 410 a, 412 a, or 414 a.

The reference numeral 420 denotes an asynchronous mobile station. Theasynchronous mobile station 420 includes a mapping entity 422, a callcontrol/mobility management (CC/MM) entity 424, a radio resourcecontroller 426, a radio link controller 428, a medium access controller430 and a physical layer 432.

The radio resource controller 426, the radio link controller 428, themedium access controller 430 and the physical layer 432 respectivelyinclude a supporting entity 426 a, 428 a, 430 a or 432 a.

The supporting entity interfaces the asynchronous radio network with thesynchronous core network.

If data is received from the synchronous core network, it is determinedwhether the data is to be transmitted to the mobile station 420 or not.If the data is to be transmitted to the mobile station, a messagemapping or parameter mapping of the data is performed in the mappingentity 404. The mapped data is provided to the radio resource controller408. The radio resource controller 408 transmits the mapped data to theCC/MM entity 406 of the mobile station 420 by using the radio resourcemessage.

The mapping entity 404 transmits an information request primitiverequesting information necessary to map or to generate parameters to thesupporting entity 408 a in the radio resource controller 408. Whenreceiving the information request primitive, the supporting entitytransmits the information requested to the mapping entity 404.

Referring to FIG. 5A, the supporting entity 104 a includes a SE serviceprocessing block 502, a layer link block 504, and a layer functionprocessing block 506.

The SE service processing block 502 provides a communication path for adata communication between the supporting entity and the mapping entity404. The SE service processing block 502 transmits the informationrequest primitive to the layer link block 504.

The layer link block 504 interfaces the SE service processing block 502with the layer function processing block 506. In other words, the layerlink block 504 maps information related to upper layers to data having aformat used in the layer function processing block 506.

The layer function processing block 506 controls a radio resourcesetting and management based on information for the layer link block504. The layer function processing block 506 obtains informationrequested by the mapping entity 404 radio resource controller. Theinformation obtained from the radio resource controller is transmittedto the mapping entity 404 through the layer function processing block506, the layer link block 504 and the SE service processing block 502.

Referring to FIG. 4 again, the radio link controller 410 controls asetting/releasing of a radio link connection based on information fromthe radio resource controller 408. If the mapping entity 404 requeststhe supporting entity 410 a in the radio link controller 410 to provideinformation necessary to a parameter mapping or a parameter generation,the supporting entity 410 a provides requested information to themapping entity 404.

Referring to FIG. 5B, the supporting entity 410 a includes a SE serviceprocessing block 512, a layer link block 514, and a layer functionprocessing block 516.

The SE service processing block 502 provides a communication path fordata communication between the supporting entity and the mapping entity404. The SE service processing block 512 transmits the informationrequest primitive to the layer link block 514.

The layer link block 514 interfaces the SE service processing block 512with the layer function processing block 516.

The layer function processing block 516 controls setting/releasing aconnection to the radio link controller and data transmission based oninformation from the layer link block 504. The radio link controller isresponsible for data transmission. The layer function processing block516 obtains information requested by the mapping entity from the radiolink controller. The information obtained from the radio link controlleris transmitted to the mapping entity through the layer functionprocessing block 516, the layer link block 514 and the SE serviceprocessing block 512.

Referring to FIG. 4 again, the medium access controller 106 controlsaccess to a physical medium based on the information obtained from theradio link controller 410. If the mapping entity 404 requests thesupporting entity 3412 a in the medium access controller 412 to provideinformation necessary to a parameter mapping or a parameter generation,the supporting entity 412 a provides requested information to themapping entity 404.

Referring to FIG. 5C, the supporting entity 412 a includes a SE serviceprocessing block 522, a layer link block 524, and a layer functionprocessing block 526.

The SE service processing block 522 provides a communication path fordata communication between the supporting entity and the mapping entity404. The SE service processing block 522 transmits the informationrequest primitive to the layer link block 526.

The layer link block 524 interfaces the SE service processing block 522with the layer function processing block 526.

The layer function processing block 526 controls reassignment of theradio resource, interfaces the physical layer 414 with the radioresource controller 408. The layer function processing block 526 obtainsinformation requested by the mapping entity from the medium accesscontroller. The information obtained from the medium access controlleris transmitted to the mapping entity through the layer functionprocessing block 526, the layer link block 524 and the SE serviceprocessing block 522.

Referring to FIG. 4 again, the physical layer 414 controls a connectionto a physical medium based on the information obtained from the mediumaccess controller 412. If the mapping entity 404 requests the supportingentity 414 a in the medium access controller 414 to provide informationnecessary to a parameter mapping or parameter generation, the supportingentity 414 a provides requested information to the mapping entity 404.

Referring to FIG. 5D, the supporting entity 414 a includes a SE serviceprocessing block 532, a layer link block 534, and a layer functionprocessing block 536.

The SE service processing block 532 provides a communication path fordata communication between the supporting entity and the mapping entity404. The SE service processing block 532 transmits the informationrequest primitive to the layer link block 534.

The layer link block 534 interfaces the SE service processing block 532with the layer function processing block 536.

The layer function processing block 536 performs a radio interface. Thelayer function processing block 536 obtains information requested by themapping entity from the physical layer. The information obtained fromthe physical layer is transmitted to the mapping entity through thelayer function processing block 536, the layer link block 534 and the SEservice processing block 532.

The mapping entity 422 in the mobile station 420 receives informationfrom the synchronous core network and transmits information to betransmitted to the synchronous core network through communicationsmessage with the mapping entity 404 in the radio access network 400. Themapping entity 422 performs the parameter mapping or the parametergeneration with is similar to be performed by the mapping entity 404.Therefore, for convenience, detailed description will be skipped in thisspecification.

FIG. 6 is a block diagram of a mapping entity in accordance with anembodiment of the present invention.

The mapping entity 404 includes a filtering block 602, a service accesspoint (SAP) block 604, a data storing/compensating block 606, aparameter mapping block 608, a message/parameter generating block 610and a discarding block 612.

The filtering block 602 selects a function necessary to generate or tomap messages received from the asynchronous radio network or theasynchronous mobile station.

The data storing/compensating block 606, if necessary, storesinformation necessary to generate or to map the message/parameter andcorrects stored message/parameter.

The parameter mapping block 608 is coupled to the filtering block 602.The parameter mapping block 608 maps the parameters of the messagesreceived from the filtering block 602 into parameters of messages fromthe asynchronous radio network, if the message is transmitted from thesynchronous core network to the asynchronous mobile station. Theparameter mapping block 608 maps the parameters of the messages receivedfrom the filtering block 602 into parameters of messages for thesynchronous core network, if the message is transmitted from theasynchronous mobile station to the synchronous core network. Then, themapped data is transmitted to the filtering block 602.

The message/parameter generating block 610 generates messages andparameters to be transmitted to the asynchronous radio network or thesynchronous core network based on the data stored onto the datastoring/compensating block 606.

In other words, the message/parameter generating block 610 generates anew message or parameter if there is no related parameter in the messageto be transmitted to the asynchronous mobile station or the synchronouscore network. In similar, the message/parameter generating block 610generates a new message or parameter if there is no related parameter inthe message to be transmitted to the synchronous core network.

The discarding block 612 discards the message/parameter not to betransmitted to the asynchronous radio network in the message/parametersreceived from the filtering block 602. The discarding block 612 allowsinformation included in the received parameter to be stored on adatabase 614 and corrects the information stored on the database 614.The discarding block 612 discards the message/parameter not to betransmitted to the asynchronous mobile station in the message/parametersreceived from the filtering block 602. The discarding block 612 allowsinformation included in the received parameters to be stored on adatabase 614 and corrects the information stored on the database 614.

The filtering block 602 transmits the message or parameter which is usedfor the filtering block 602 or to be transmitted to the asynchronousmobile station 420 to the SAP block 604. The message or the parametertransmitted to the SAP block 604 is a message or a parameter which ismapped or generated in the parameter mapping block 608, themessage/parameter generating block 610 or the discarding block 612.

The SAP block provides a patch for a data transmission between thefiltering block 602 and the radio resource controller. The SAP block 604manages an asynchronous service access point function.

When transmitting the message/parameter to the lower layers, ifpossible, the message/parameter is transmitted to the radio resourcescontroller by the RRC SAP block. If there is a function which is notdefined in the RRC SAP block, the message/parameter is transmitted tothe radio resource controller by a supporting entity (SE) SAP functionof the supporting entity 604 a.

Then, the RRC transfers the received message to its lower layers, ortransmits the received message to the CC/MM 424 of the asynchronousmobile station 420 by using a RRC message.

The mapping entity 422 included in the asynchronous mobile station haselements and functions similar to those of the asynchronous radionetwork. Therefore, for convenience, detailed description about themapping entity 422 will be skipped in the specification.

FIG. 7 is a flow chart illustrating a method for transmitting a messagebetween an asynchronous radio network and a synchronous core network.

First, a message is received from a synchronous core network in stepS702. The process goes to step S704 to select a function necessary totransmit the received message to the asynchronous mobile station. Inother words, one of a message mapping function, a message/parametergenerating function, a message/parameter storing function, or a messageparameter discarding function is selected.

At step S706, it is determined whether there is a message to betransmitted to the asynchronous mobile station. If there is no messageto be transmitted to the asynchronous mobile station, the parametersincluded in the message are stored onto the database 614 and the messageis discarded at step S708.

If there is a message to be transmitted to the asynchronous mobilestation, it is determined whether there is a related parameter in thereceived message at step S710.

If there is the related parameter in the received message, the parameterfor the synchronous message is mapped to a parameter for theasynchronous message at step 712.

If there is no related parameter, a parameter for the asynchronousmessage is generated by using the stored parameter at step 714.

Then, it is determined whether the mapped or generated message can betransmitted by using a conventional RRC SAP function at step S716. Ifpossible, the message is transmitted to the RRC by using theconventional RRC SAP function at step S718. If not, the message istransmitted to the RRC by using the supporting entity (SE) SAP functionat step S720.

The RRC transmits the generated message to the CC/MM entity of theasynchronous mobile station by using the RRC message at step S722.

FIG. 8 is a block diagram of a CC/MM mapper for mapping a callcontrol/mobile management (CC/MM) message between an asynchronous radionetwork and a synchronous core network.

Hereinafter, a method and apparatus for interfacing a synchronous corenetwork with a radio network in accordance with another embodiment ofthe preset invention will be described with reference to FIGS. 8 to 12.

The CC/MM mapper includes a discriminator 842 a bypass parameterprocessing block (BPP) 844 and an action parameter processing block(APP) 846.

The discriminator 840 monitors a CC/MM message and divides the messageinto parameters to by bypassed and parameters not to be bypassed.

The BPP 844 encapsulates the parameter to be bypassed or maps theparameter in accordance with a message format used in the radio resourcecontroller of the asynchronous radio network. Then, the BPP 844transmits encapsulated or mapped parameter to the asynchronous mobilestation.

The APP 846 stores onto the database 848 or transmits information to beprocessed in the asynchronous radio network to lower protocol layers,i.e., the radio resource controller 850, the radio link controller 852and the medium access controller 854.

FIG. 9 is a flow chart illustrating a method for determining whether theCC/MM message is bypassed or not.

First, a message for CC/MM is received from the synchronous core networkat step S902. The discriminator divides the message into parameters tobe bypassed and parameters not to be bypassed at step S904. Then, it isdetermined whether the parameter is to be bypassed or not at step S906.If the message is to be bypassed, the message is transmitted to the BPP844 at step S908. If not, the message is transmitted to the APP 846 atstep S910.

FIG. 10 is a flow chart illustrating a method for mapping synchronousCC/MM message to asynchronous CC/MM message.

The BPP 844 receives a message to be bypassed from the discriminator atstep S1002, and determines whether the message can be converted by amapping or an encapsulation at step S1004. If the message cannot beconverted by the mapping method, in other words, if the message can beconverted by the encapsulating method, the BPP 844 encapsulates themessage in accordance with the data format of the asynchronous radioresource controller and bypasses an encapsulated message to theasynchronous mobile station at step S1 008.

If the message should be converted by the mapping method, the BPP 844maps the synchronous parameter into an asynchronous parameter anddetermines whether a size of the mapped parameter is equal to apredetermined size at steps S1006 and S1010. If the size of the mappedparameter is equal to the predetermined size, the BPP 844 arranges themapped parameters in the order of the synchronous message and transmitsthe mapped parameter to the asynchronous mobile station at step S1014.If not, the BPP 844 adjusts a length of the mapped parameter inaccordance with the predetermined size at step S1012. Then, the BPP 844arranges the parameters in the order of the asynchronous message andtransmits the parameter having the same length with the predeterminedsize at steps S1012 and S1014.

FIG. 11 is a flow chart illustrating a method for processing a parameternot to be bypassed.

The APP 846 receives a parameter not to be bypassed, i.e., a parameterused in the asynchronous radio network at step S1102, and determineswhether the parameter of the message is to be processed at step S1104.

If the parameter is to be processed, the APP processes the parameters atstep S1106. If not, the APP stores the message onto the database at step1108.

FIG. 12 is a diagram showing operations for converting synchronousauthentication request message to asynchronous authentication requestmessage.

If an authentication request message is received at a synchronous CC/MMentity 830 a included in a synchronous core network, a call processingblock 840 of an asynchronous base station determines whether theauthentication request message should be bypassed or not in order to betransmitted to an asynchronous CC/MM entity 810 a in a asynchronousmobile station.

The discriminator 842 divides the authentication request message intoparameters to be bypassed and parameters to be processed in theasynchronous base station. For example, parameters to be processed inthe asynchronous base station include a mobility identity, a last pagingframe class, etc. the parameters to be bypassed include a message type,an authentication challenge parameter, etc.

The parameters to be bypassed are transmitted to the BPP 844. Theparameters to be processed in the asynchronous base station aretransmitted to the APP 846.

The BPP 844 receives the message to be bypassed from the discriminatorand determines whether the message can be converted by a mapping or anencapsulating method. If the message cannot be converted by the mappingmethod, in other words, if the message should be converted by theencapsulating method, the BPP 844 encapsulates the parameter inaccordance with the data format of the asynchronous radio resourcecontroller and bypasses the encapsulated parameter to the asynchronousmobile station.

If the parameter should be converted by the mapping method, the BPP 844maps the synchronous parameter into an asynchronous parameter anddetermines whether a size of the mapped parameter is equal to apredetermined size. If the size of the mapped parameter is equal to thepredetermined size, the BPP transmits the mapped parameter to theasynchronous mobile station. If not, the BPP 844 adjusts a length of themapped parameter in accordance with the predetermined size by usingpadding. The BPP 844 bypasses the parameter having the same length withthe predetermined size in order to transmit the parameter.

If the APP 846 receives a message not to be bypassed, i.e., theparameter used in the asynchronous base station, and determines whetherthe parameter is to be processed in a lower layer, for example, RRC, RLCor MAC. If the parameter is to be processed in lower layer, the APP 846allows the parameter to be processed in the lower layer, for example,RRC, RLC or MAC.

If the parameters of the message are to be reused, the APP 846 storesthe message onto the database. When a response message to theauthentication request message is received from the asynchronous mobilestation, the asynchronous base station transmits the response message tothe synchronous core network based on the stored parameters.

Although the preferred embodiments of the invention have been disclosedfor illustrative purpose, those skilled in the art will be appreciatethe various modifications, additions and substitutions are possible,without departing from the scope and spirit of the invention asdisclosed in the accompanying claims.

1. A method comprising: receiving a first control message from a firstnetwork at a first network element in communication with the firstnetwork and a second network, wherein the first network is configured tooperate according to a first protocol, wherein the second network isconfigured to operate according a second protocol, and wherein the firstcontrol message includes a message parameter; determining, at the firstnetwork element, whether the first control message includes a messageparameter associated with a second network element in communication withthe second network; in response to determining that the first controlmessage includes the message parameter associated with the secondnetwork element, generating a second control message based on the firstcontrol message at the first network element, wherein the generatingcomprises mapping a message parameter from a set of stored messageparameters to a message parameter in the second control message, andwherein the second control message is configured for transmission to thesecond network element via the second network.
 2. The method of claim 1,further comprising: determining whether the first control messageincludes a message parameter associated with the first network element;and in response to determining that the first control message includesthe message parameter associated with the first network element and themessage parameter associated with the second network element, storingthe at least one message parameter associated with the first networkelement at the first network element.
 3. The method of claim 1, whereinone of the first network or the second network is a synchronous corenetwork, and wherein the other of the first network or the secondnetwork is an asynchronous wireless network.
 4. The method of claim 1,wherein the second control message includes a message parameter, andwherein generating the second control message comprises mapping themessage parameter of the first control message to the message parameterof the second control message.
 5. The method of claim 4, wherein mappingthe message parameter of the first control message to the messageparameter of the second control message comprises adjusting a length ofthe message parameter of the first control message.
 6. The method ofclaim 1, wherein the second control message includes a messageparameter, and wherein generating the second control message comprisesmapping a message parameter from a set of message parameters stored atthe first network element to the message parameter of the second controlmessage.
 7. The method of claim 1, wherein the second control messageincludes a message parameter, and wherein generating the second controlmessage comprises encapsulating the message parameter of the firstcontrol message in the second control message.
 8. The method of claim 1,wherein the first network element is a wireless base station, andwherein the second network element is a communications device configuredto communicate with the wireless base station.
 9. The method of claim 1,wherein the first control message is related to a call control andmobility management functionality in a wireless network.
 10. A systemcomprising: a first network element configured to process datatransmissions between a first network and a second network, wherein thefirst network is configured to operate according to a first protocol andthe second network is configured to operate according to a secondprotocol, wherein the first network element comprises: communicationscircuitry configured to receive a first control message from the firstnetwork, wherein the first control message includes a message parameter;processing circuitry configured to determine whether the first controlmessage includes a message parameter associated with a second networkelement in communication with the second network; and mapping circuitryconfigured to generate a second control message based on the firstcontrol message in response to the processing circuitry determining thatthe first control message includes the message parameter associated withthe second network element.
 11. The system of claim 10, wherein theprocessing circuitry is further configured to determine whether thefirst control message includes a message parameter associated with thefirst network element, and wherein the storage circuitry is furtherconfigured to store the message parameter associated with the firstnetwork element in response to the processing circuitry determining thatthe first control message includes the message parameter associated withthe second network element.
 12. The system of claim 10, wherein one ofthe first network or the second network is a synchronous core network,and wherein the other of the first network or the second network is anasynchronous wireless network.
 13. The system of claim 10, wherein thesecond control message includes a message parameter, and wherein themapping circuitry is further configured to map the message parameter ofthe first control message to the message parameter of the second controlmessage.
 14. The system of claim 13, wherein the mapping circuitry isfurther configured to adjust a length of the message parameter of thefirst control message.
 15. The system of claim 10, wherein the secondcontrol message includes a message parameter, and wherein the mappingcircuitry is further configured to map a message parameter from a set ofstored message parameters to the message parameter of the second controlmessage.
 16. The system of claim 10, wherein the second control messageincludes a message parameter, and wherein the mapping circuitry isfurther configured to encapsulate the message parameter of the firstcontrol message in the second control message.
 17. The system of claim10, wherein the first network element is a wireless base station, andwherein the second network element is a communications device configuredto communicate with the wireless base station.
 18. The system of claim10, wherein the first control message is related to a call control andmobility management functionality in a wireless network.
 19. Anon-transitory computer-readable medium having instructions storedthereon, the instructions comprising: instructions to receive a firstcontrol message from a first network at a first network element incommunication with the first network and a second network, wherein thefirst network is configured to operate according to a first protocol,wherein the second network is configured to operate according a secondprotocol, and wherein the first control message includes a messageparameter; instructions to determine whether the first control messageincludes a message parameter associated with a second network element incommunication with the second network; and instructions to generate asecond control message based on the first control message in response todetermining that the first control message includes the messageparameter associated with the second network element, wherein thegenerating comprises mapping a message parameter from a set of storedmessage parameters to a message parameter in the second control message,and wherein the second control message is configured for transmission tothe second network element via the second network.
 20. Thenon-transitory computer-readable medium of claim 19, further comprising:instructions to determine whether the first control message includes amessage parameter associated with the first network element; andinstructions to store the at least one message parameter associated withthe first network element at the first network element in response todetermining that the first control message includes the messageparameter associated with the first network element and the messageparameter associated with the second network element.
 21. Thenon-transitory computer-readable medium of claim 19, wherein one of thefirst network or the second network is a synchronous core network, andwherein the other of the first network or the second network is anasynchronous wireless network.
 22. The non-transitory computer-readablemedium of claim 19, wherein the second control message includes amessage parameter, and wherein the instructions to generate the secondcontrol message comprises instructions to map the message parameter ofthe first control message to the message parameter of the second controlmessage.
 23. The non-transitory computer-readable medium of claim 22,wherein the instructions to map the message parameter of the firstcontrol message to the message parameter of the second control messagecomprises instructions to adjust a length of the message parameter ofthe first control message.
 24. The non-transitory computer-readablemedium of claim 19, wherein the second control message includes amessage parameter, and wherein the instructions to generate the secondcontrol message comprises instructions to map a message parameter from aset of stored message parameters to the message parameter of the secondcontrol message.
 25. The non-transitory computer-readable medium ofclaim 19, wherein the second control message includes a messageparameter, and wherein the instructions to generate the second controlmessage comprises instructions to encapsulate the message parameter ofthe first control message in the second control message.
 26. Thenon-transitory computer-readable medium of claim 19, wherein the firstnetwork element is a wireless base station, and wherein the secondnetwork element is a communications device configured to communicatewith the wireless base station.
 27. The non-transitory computer-readablemedium of claim 19, wherein the first control message is related to acall control and mobility management functionality in a wirelessnetwork.